Pre-requirements

• feat: enforce and normalize package dependencies #316

New Behaviour

migrates releases from beachball to NX Release Plans which add various needed features to our release process

• dry-run mode for all release steps ( including npm publish )
• completely mitigates out of sync release issues caused by npm publish errors
  • we can re-trigger Publish indefinitely until registry contains all required assets that were part of the pipeline
• dynamically configurable release trigger
  • release can be filtered for particular package, package group or by rich filtering options available
• security:
  • de-chunked releases steps are ready for GHA/ADO split as a follow-up
  • enables mitigation of PAT usage for upcoming manual release trigger as a follow-up
• perf:
  • mitigates Consider alternative to append-only CHANGELOG.md files beachball#978
  • no branch checkouts and back during release

New Release pipeline architecture:

flowchart LR

subgraph Release
assets['build,lint,test,type-check']-->bump-versions-->generate-changelogs-->push-to-origin
end

subgraph Publish
build-production-assets-->npm-publish
end


Release-->RS
RS -- yes --> Publish
RS -- no --> FAIL

Publish-->PS
PS -- yes --> OK
PS -- no --> FAIL



RS@{ shape: diamond, label: "Release success?" }
PS@{ shape: diamond, label: "Publish success?" }
OK["pipeline success"]
FAIL["pipeline failure"]

TODO:

• port all beachball change files to version plans
• remove all CHANGELOG.json files

Release plans Missing features:

• NX release: support `dependantChangeType` functionality for release plans nrwl/nx#29716
• NX release: support `dissalowedChangeType` functionality for release plans nrwl/nx#29715

NX release cli issues:

• release: root release command is missing --git-push and --git-remote available in sub-commands nrwl/nx#30551
• release: executing release wont run nx-release-publish target and it's dependencies nrwl/nx#30552

Dependency-Check rule issues

note: this rule goes hand in hand with enabling version plans as bumping dependants is propagated only through projects that have properly specified versions within package.json ( its not using actual ProjectGraph )

• @nx/dependency-checks: add option for allowing dependencies to be satisfied by depending on their direct dependents nrwl/nx#29853
• @nx/dependency-checks: invalid lint errors of missing build artifact dependencies nrwl/nx#29856
• docs: @nx/dependency-checks cannot handle different build target names when resolving project dependencies nrwl/nx#29439
• @nx/dependency-checks + tslib + swc listing problems nrwl/nx#18033